feat(live-share): add temporary collaboration rooms#203
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying markdown-viewer with
|
| Latest commit: |
f5e7771
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://23c46850.markdown-viewer.pages.dev |
| Branch Preview URL: | https://codex-live-share.markdown-viewer.pages.dev |
|
Follow-up for cross-user Live Share behavior:
Validation:
Note: the in-app browser automation exposes a single tab id when asked to open multiple tabs, so I could not use it as a trustworthy two-client remote-collaboration test. The previous same-browser sync result was not a valid proof of cross-user signaling. |
Deploying markdownviewer with
|
| Latest commit: |
55468b7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://70d55c4e.markdownviewer.pages.dev |
| Branch Preview URL: | https://codex-live-share.markdownviewer.pages.dev |
|
Deploy-fix follow-up: Cloudflare Pages failed because the root
I removed the root Pages Validation after the fix:
|
What changed
/live-signalfor peer discovery only.Why
Live collaboration needs temporary signaling for WebRTC peer discovery, but the Markdown document should not be stored in a database, server file, or persistent document backend.
Impact
Users can start a temporary editable room, copy a
#live=room.secretinvite link, and collaborate on Markdown text while the room is active. Everyone with the live room link can edit.Validation
node --check script.jsnode --check functions/live-signal/[[path]].jsgit diff --check